Systems and methods for predictive selection of pause points

ABSTRACT

Systems and methods are described for determining that a plurality of user profiles, stored in the memory, are associated with an account of a media application; generating for presentation a media asset during a first consumption session associated with the account; generating for presentation a selectable option to associate a current progress point of the media asset with one or more of the plurality of user profiles associated with the account; receiving a selection of one or more of the plurality of user profiles via the selectable option; during a second consumption session, receiving a request for accessing the media asset; and in response to determining that the second consumption session is associated with the selected one or more user profiles, resuming the media asset from the progress point associated with the selectable option.

BACKGROUND

This disclosure is directed to systems and methods for predictiveselection of pause points. In particular, techniques are disclosed forselecting a pause point from which to resume a media asset from amongmultiple pause points associated with the media asset based onidentified user interface inputs, and providing an option to associate apause point from one user profile with another user profile.

SUMMARY

Modem media distribution systems enable a user to access more mediacontent than ever before, and on more devices than ever before. Somemedia content providers enable a user to subscribe to an account that isassociated with multiple user profiles. For example, multiple userswithin the same household can each have his or her own profile withinthe media content provider account, such that each profile tracks therespective user’s viewing histories separately. On the other hand, somemedia content providers only offer a single shared user profile thattracks the collective viewing histories of a household, ratherdifferentiating between the viewing histories of individual users.

Each of these approaches has drawbacks, however. For example, in thecontext of a shared media profile, if multiple users have been viewingthe same media asset at different times and stopped viewing the mediaasset at different pause points, it is difficult for the media contentprovider to track viewing progress of the multiple users, i.e., themedia content provider may store only one of such pause points. In thisscenario, at least one of the user’s pause points may not be saved andthus that user would not be able to resume the media asset from where heor she left off, and would need to rewind or fast-forward the mediaasset to navigate to where he or she left off, which may be a cumbersometask that is frustrating to users, and may waste bandwidth, computingresources and networking resources. While a shared media accountproviding for individual user profiles may allow multiple pause pointsto be stored in respective user profiles, some users may not have aprofile (e.g., a guest of the household) or may be accidentallyaccessing the user profile of another user. In addition, users oftenconsume content together, but a first user may need to stop watching thecontent for a variety of reasons, while a second user (e.g., associatedwith a user profile that requested access to the content) may wish tocontinue watching the content. However, in these circumstances, themedia content provider does not provide a mechanism for the first userthat needs to stop watching the content to preserve the progress pointof the content at which he or she stopped viewing the content with theother user (e.g., the progress point may only be stored for the seconduser).

To overcome these problems, systems and methods are provided herein forstoring an identification of a first pause point of a media assetassociated with a first user interaction profile; storing anidentification of a second pause point of the media asset associatedwith a second user interaction profile; receiving a request to accessthe media asset during a current consumption session; identifying userinterface inputs received during the current consumption session;selecting one of the first pause point and the second pause point as aselected pause point based on determining whether the identified userinterface inputs match user interface inputs associated with the firstuser interaction profile or the second user interaction profile; andgenerating for presentation the media asset starting from the selectedpause point. In some embodiments, the media asset may be generated forpresentation from the selected pause point seamlessly, without receivinguser or user interface input explicitly selecting which pause point toresume from. In some embodiments, a preview of one or more framesassociated with the pause point may be provided to the user, to enablereceiving a confirmatory selection from the user indicating that aparticular pause point is where he or she left off.

Such aspects enable, e.g., in the context of a media profile shared bymultiple users, providing a media asset to a user from a progress pointfrom which the user left off, without requiring the user to fast-forwardor rewind through the media asset to locate his or her previousposition, e.g., due to another user of the media profile having consumedthe media asset until a different progress point of the media asset.Such features may avoid the expenditure of unnecessary bandwidth,computing resources and networking resources, which may be otherwiseexpended if the user needs to navigate through the media asset todiscover the portion he or she left off at, as well as avoiding thepresentation of content the user has not yet viewed (e.g., spoilers)that the user may encounter while attempting to discover where he or sheleft off. The correct pause point may be selected based on analyzingnavigation patterns on a user interface of an application provided by amedia content provider, which may preserve the privacy of the user(e.g., as opposed to identifying a user based on captured images of theuser or other biometric information). In some embodiments, a preview orrecap of frames associated with the pause point may be presented to theuser to enable the user to verify the correct pause point he or she leftoff at.

In addition, systems and methods are provided herein for determiningthat a plurality of user profiles are associated with an account of amedia application; generating for presentation a media asset during afirst consumption session associated with the account; generating forpresentation a selectable option to associate a current progress pointof the media asset with one or more of the plurality of user profilesassociated with the account; receiving a selection of one or more of theplurality of user profiles via the selectable option; during a secondconsumption session, receiving a request for accessing the media asset;and in response to determining that the second consumption session isassociated with the selected one or more user profiles, resuming themedia asset from the progress point associated with the selectableoption.

Such aspects enable, e.g., in the context of a media account shared bymultiple users having respective user profiles as part of the account,preserving a progress point he or she reached while consuming contentwith another user associated with the media account. For example, in thecontext of a family consumption session or group watching session, if agroup begins consuming content together on one profile, but a user needsto stop watching the content (e.g., to leave for work, to cook dinner,etc.), such user may be provided with the ability to associate the pausepoint he or she left off at with his or her profile, in order to laterfinish consuming the content from the saved pause point. Thus, such usermay avoid the need to fast-forward or rewind through the media asset tolocate his or her previous position, as well as avoid the need toremember which media asset (e.g., which episode of a series) he or shewas watching with the group in order to locate the media asset. Inaddition, such features may avoid the expenditure of unnecessarybandwidth, computing resources and networking resources, that may beotherwise expended if the user needs to navigate through the media assetto discover the point he or she left off at and/or the media assetitself, as well as avoiding the presentation of content the user has notyet viewed (e.g., spoilers) that the user may encounter while attemptingto discover where he or she left off.

In some embodiments, the provided systems and methods further comprisemonitoring user interface inputs received over time, and determining,based on the monitored user interface inputs, a plurality of userinteraction profiles for respective users.

In some aspects of this disclosure, generating for presentation themedia asset starting from the selected pause point comprises generatingfor presentation a preview frame associated with the selected pausepoint.

In some embodiments, the provided systems and methods further comprisedetermining a confidence score associated with whether the userinterface inputs match user interface inputs associated with the firstuser interaction profile or the second user interaction profile; and inresponse to determining the confidence score exceeds a predefinedthreshold, generating for presentation the media asset from the firstpause point without generating for presentation a preview of the mediaasset.

In some aspects of this disclosure, the provided systems and methodsfurther comprise determining a confidence score associated with whetherthe user interface inputs match user interface inputs associated withthe first user interaction profile or the second user interactionprofile, and, in response to determining the confidence score exceeds apredefined threshold, pre-fetching a portion of the media assetassociated with the selected pause point. Such aspects enablepre-buffering a media asset from an anticipated resume position, e.g.,the system may begin buffering as soon as the user interface inputs arecorrelated to a particular user interaction profile and pause pointstored for the media asset in connection with such profile.

In some embodiments, the first user interaction profile and second userinteraction profile respectively comprise a plurality of time stampsassociated with a plurality of times during which the media asset andrelated media assets were accessed and navigation patterns associatedwith user interface inputs. In some embodiments, the navigation patternsindicate, for the first user interaction profile and the second userinteraction profile, one or more of a most commonly accessed portion,whether accessing media assets is more commonly performed via searchquery commands or scroll commands, a scrolling rate, a frequency ofreceiving requests to perform trick-play functions, past durations ofconsumption sessions, and frequency of skipping supplemental content.

In some aspects of this disclosure, the media asset is being generatedfor display on a first device, and the first pause point is associatedwith pausing the media asset, generated for display on the first device,based on receiving a pause command from a second device. In some aspectsof this disclosure, determining whether the identified user interfaceinputs match identified user interface inputs associated with the firstuser interaction profile or the second user interaction profile maycomprise determining the request to access the media asset was receivedfrom the second device.

In some embodiments, the provided systems and methods further comprisegenerating for presentation respective previews for each pause point ofthe media asset. In some embodiments, generating for presentationrespective previews for each pause point of the media asset comprisesgenerating for presentation, for each pause point, a frame of the mediaasset prior to the pause point, wherein the preview for the second pausepoint comprises a frame of the media asset occurring prior to the secondpause point and after the first pause point.

In some aspects of this disclosure, the provided systems and methodsfurther comprise in response to receiving the request for accessing themedia asset and determining that the second consumption session isassociated with the selected one or more user profiles, providing aselectable option to resume the media asset from the progress pointassociated with the selectable option.

In some embodiments, the media asset is generated for presentation on afirst device, and the selectable option is generated for presentation onthe first device.

In some aspects of this disclosure, the media asset is generated forpresentation on a first device, and the selectable option is generatedfor presentation on a second device in the vicinity of the first device.

In some aspects of this disclosure, the provided systems and methodsfurther comprise determining that a plurality of users associated withrespective user profiles of the plurality of user profiles are consumingthe media asset during the first consumption session.

In some embodiments, determining that the plurality of users associatedwith respective user profiles of the plurality of user profiles areconsuming the media asset during the first consumption session comprisesdetermining that a first user profile initiated the first consumptionsession and determining that a second user profile comprises anindication that media assets related to the media asset of the firstconsumption session were previously consumed.

In some aspects of this disclosure, determining that the plurality ofusers associated with respective user profiles of the plurality of userprofiles are consuming the media asset during the first consumptionsession comprises determining, based on sensor data, that usersassociated with a first user profile and a second user profile,respectively, are consuming the media asset during the first consumptionsession.

In some embodiments, determining that the plurality of users associatedwith respective user profiles of the plurality of user profiles areconsuming the media asset during the first consumption session comprisesreceiving input indicating that the users associated with the first userprofile and the second user profile, respectively, are consuming themedia asset during the first consumption session.

In some aspects of this disclosure, the provided systems and methodsfurther comprise determining that a user associated with a particularuser profile is not consuming the media asset during the firstconsumption session; and in response to determining that the userassociated with the particular user profile is not consuming the mediaasset during the first consumption session, declining to generate forpresentation the selectable option. In some embodiments, determiningthat the user associated with the particular user profile is notconsuming the media asset during the first consumption session comprisesdetermining that media assets indicated in the particular user profileare not related to the media asset being consumed during the firstconsumption session.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure, in accordance with one or more variousembodiments, is described in detail with reference to the followingfigures. The drawings are provided for purposes of illustration only andmerely depict typical or example embodiments. These drawings areprovided to facilitate an understanding of the concepts disclosed hereinand should not be considered limiting of the breadth, scope, orapplicability of these concepts. It should be noted that for clarity andease of illustration, these drawings are not necessarily made to scale.

FIG. 1 shows a block diagram of an illustrative system for generatingfor presentation a media asset starting from a selected pause point, inaccordance with some embodiments of this disclosure.

FIG. 2 shows illustrative user interfaces for presenting previewsassociated with pause points of media assets, in accordance with someembodiments of this disclosure;

FIG. 3 shows a block diagram of an illustrative system for associating acurrent progress point of a media asset with one or more user profilesassociated with a media application account, in accordance with someembodiments of this disclosure;

FIG. 4 shows illustrative data structures of user interaction profilesstored in a user consumption data database, in accordance with someembodiments of this disclosure;

FIG. 5 shows an illustrative user equipment device, in accordance withsome embodiments of this disclosure;

FIG. 6 shows a system, in accordance with some embodiments of thisdisclosure;

FIG. 7 is a flowchart of a detailed illustrative process for generatingfor presentation a media asset starting from a selected pause point, inaccordance with some embodiments of this disclosure;

FIG. 8 is a flowchart of a detailed illustrative process for generatingfor presentation a media asset starting from a selected pause point, inaccordance with some embodiments of this disclosure;

FIG. 9 is a flowchart of a detailed illustrative process for associatinga current progress point of a media asset with one or more user profilesassociated with a media application account, in accordance with someembodiments of this disclosure;

FIG. 10 is a flowchart of a detailed illustrative process fordetermining whether to present a selectable option to associate acurrent progress point of a media asset with one or more user profilesassociated with a media application account, in accordance with someembodiments of this disclosure; and

FIG. 11 is a flowchart of a detailed illustrative process for storing anew pause point with a preview, in accordance with some embodiments ofthis disclosure.

DETAILED DESCRIPTION

As referred to herein, the term “media asset” should be understood torefer to an electronically consumable user asset, e.g., televisionprogramming, as well as pay-per-view programs, on-demand programs (as invideo-on-demand (VOD) systems), Internet content (e.g., streamingcontent, downloadable content, webcasts, etc.), augmented realitycontent, virtual reality content, video clips, audio, playlists,websites, articles, electronic books, blogs, social media, applications,games, and/or any other media or multimedia, and/or combination of theabove.

FIG. 1 shows a block diagram of an illustrative system 100 forgenerating for presentation a media asset starting from a selected pausepoint, in accordance with some embodiments of this disclosure. A mediaapplication (e.g., executed at least in part on user equipment device105 and/or a remote server, such as, for example, media content source602 and/or server 604) may generate for display user interface 103comprising one or more media asset identifiers 108, 110, 112, 114corresponding to respective media assets, during a consumption sessionassociated with the media application and user 102. In some embodiments,media asset identifiers 108 and 110 may be associated with media assetcategory 116, and media asset identifiers 112 and 114 may be associatedwith media asset category 118. User interface 103 may comprise searchbar 120 at which queries for media assets may be received from a user.Media asset 126 may be generated for display from a broadcast or streamreceived at user equipment device 105 in association with the mediaapplication, or from a recording stored in a memory of user equipmentdevice 105 and/or a remote server. User equipment device 105 may be,e.g., a television and/or may include an integrated display, e.g., on asmartphone or tablet, or may be connected to an external display device,e.g., a television.

User interface 107 may be provided to user 104 in a separate consumptionsession associated with the media application and user 104, e.g.,occurring prior to, or subsequent to, the consumption session of user102. Such separate consumption session may be associated with userequipment device 105 or any other suitable device capable of accessingthe shared media account or profile. In some embodiments, users 102 and104 may be accessing the media application using a shared media accountor shared media profile, e.g., accessible via the same login credentialsof a user with a media content provider. In other words, the mediaapplication may not be able to determine which of user 102 or user 104is accessing the media application on the basis of received logincredentials or based on a selected user profile.

At 122, the media application may monitor user interface inputs receivedfrom users 102 and 104 to generate respective user interaction profiles,and cause such user interaction profiles to be stored in database 125,as shown in more detail in connection with FIG. 4 . User interfaceinputs may be monitored by the media application over any suitableperiod of time. In some embodiments, the user interaction profiles maybe transparent to the user, e.g., users 102 and user 104 may interactwith the media application by logging in to a shared user account orprofile that may not be specific to user 102 or user 104. The mediaapplication may monitor, for inclusion in the user interaction profiles,any suitable number of types of user interface inputs, e.g., a mostcommonly accessed portion of the media application, whether accessingmedia assets is more commonly performed via search query commands orscroll commands, a scrolling rate and/or scrolling depth, a frequency ofreceiving requests to perform trick-play functions, past durations ofconsumption sessions, frequency of skipping supplemental content, etc.For example, the media application may build user interaction profilesfor users 102 and 104 comprising historical navigation patterns andconsumption history for each user, such that the media application maypredict whether user 102 or user 104 is accessing the media applicationduring a current consumption session by comparing user interface inputsreceived during the current consumption session to user interface inputsassociated with the respective user interaction profiles. The mediaapplication may monitor user interface inputs received prior to theconsumption sessions of users 102 and 104 depicted in FIG. 1 , as wellas subsequent to such consumption sessions.

As shown at user interfaces 109 and 111 separately corresponding toconsumption sessions of users 102 and 104, respectively, the mediaapplication may generate for presentation media asset 126 (e.g., anepisode of the media asset associated with media asset identifier 108).The media application may generate for presentation media asset 126based on receiving input selecting identifier 108 shown in media assetcategory 116 or based on receiving a query via search bar 120 requestingaccess to media asset 126. The media application may receive the queryin any suitable format (e.g., text-based input via a remote control orkeyboard or other input device, audio or voice input, touch input,biometric input, or any combination thereof) via a suitable interface(e.g., input interface 510, microphone 518 of FIG. 5 , etc.).

At 132, the media application may receive a pause command from user 102,e.g., associated with pause icon 128, to pause media asset 126 at pausepoint 124 within the presentation of media asset 126. In addition, at132, the media application may receive (e.g., at a later time than thepause command is received from user 102) a pause command from user 104,e.g., associated with pause icon 128, to pause media asset 126 at pausepoint 130 within the presentation of media asset 126. Pause point 130may correspond to a different location within media asset 126 than pausepoint 124, e.g., pause point 130 may occur prior to, or after, pausepoint 124 within media asset 126. In some embodiments, the request toaccess media asset 126 is received from user 104 subsequent to therequest to access media asset 126 received from user 102 and/or thepause command associated with icon 128 from user 102. In such instance,the media application may determine to play media asset 126 from thebeginning, as opposed to from the pause point associated with user 102,based on determining that user interface inputs associated with theconsumption session of user 104 do not correspond to user interfaceinputs corresponding to the first user interaction profile associatedwith user 102. Indicators of pause point 124 and pause point 130 may bestored in connection with the respective user interaction profiles indatabase 125. In some embodiments, pause points 124 and/or 130 may bestored in response to, e.g., a user exiting the media application, adevice associated with playing of media asset 126 being powered off, orany request to otherwise cease or stop access of media asset 126.

At 134, the media application may determine that another consumptionsession has been initiated, e.g., a current consumption session,occurring subsequent to the consumption sessions during which pausepoint 124 and pause point 130 were stored in connection with therespective user interaction profiles in database 125. In someembodiments, the media application illustrated in FIG. 1 may provide ashared user account or profile such that the media application may notbe able to determine which of user 102 or user 104 is using the mediaapplication based on login credentials alone, and the particular userdevice 105 being used may not be indicative of which of user 102 or user104 is associated with the current consumption session. The mediaapplication may identify user interface inputs during the currentconsumption session, and receive a request to access the media asset.

At 136, the media application may compare the identified user interfaceinputs during the current consumption session to user interface inputsassociated with the user interaction profiles. For example, during thecurrent consumption session, the media application may receive selectionof media asset 126 via identifier 108 contained in media asset category116, in which case the media application may determine that the currentconsumption session corresponds to the first user interaction profile,e.g., if the first user interaction profile is commonly associated withselecting media assets from media asset category 116, and/or consumptionsessions at the particular time of day or day of the week of the currentconsumption session. On the other hand, during the current consumptionsession, the media application may receive selection of media asset 126discovered by way of a query via search bar 120, in which case the mediaapplication may determine that the current consumption sessioncorresponds to the second user interaction profile, e.g., if the seconduser interaction profile is commonly associated with selecting mediaassets discovered by way of a query via search bar 120, and/orconsumption sessions at the particular time of day or day of the week ofthe current consumption session.

The media application may select one of pause point 124 or pause point130 based on the comparison of the identified user interface inputs. Forexample, in response to determining that the user interface inputs ofthe current consumption session match user interface inputs stored atuser consumption database 125 in connection with the first userinteraction profile, the media application may cause media application126 to be generated for display from pause point 124 associated with thefirst user interaction profile. In some embodiments, the mediaapplication may cause media asset 126 to be generated for display frompause point 124 automatically in response to the determination that theuser interface inputs of the current consumption session match userinterface associated with the first user interaction profile, or aselectable option may be generated for presentation at user equipmentdevice 105 for user confirmation of pause point 124. In someembodiments, one or more previews of pause point 124 may be generatedfor display by the media application, as discussed in more detail inconnection with FIG. 2 . In some embodiments, if during the currentconsumption session the media application receives input to restart aparticular media asset from the beginning, the media application may usethis as an indication that the consumption session is associated with auser interaction profile that has not yet viewed the media asset andthus is not associated with a stored pause point. In some embodiments, auser interaction profile associated with a current consumption sessionmay be identified based on detections by one or more sensors (e.g., acamera attached to user equipment device 105, a smart lock associatedwith a room in which user equipment device 105 is positioned, detectinga user device of a particular user, such as a mobile phone, is in avicinity of user equipment device 105, etc.), such as by comparingsensor data determined by the one or more sensors with informationstored in association with the user interaction profiles.

FIG. 2 shows illustrative user interfaces for presenting previewsassociated with pause points of media assets, in accordance with someembodiments of this disclosure. It should be noted that the embodimentsdiscussed in connection with FIG. 2 may be implemented alternatively orin addition to the embodiments discussed in connection with FIG. 1 . Themedia application may generate for presentation user interface 201 inconnection with media asset 126. User interface 201 may compriseidentifiers 202 and 204 respectively associated with pause points 124and 130 of media asset 126, an indication of media asset 126, one ormore frames of preview 208 associated with pause point 124 indicated at202, one or more frames of preview 210 associated with pause point 130indicated at 204, and a selectable option 212 to restart thepresentation of media asset 126 from a beginning of media asset 126. Insome embodiments, the preview frames may be associated with a short clip(e.g., 5-10 seconds) prior to and/or encompassing a particular pausepoint, an animation associated with the particular pause point, stillimages of one or more frames associated with the particular pause point,audio associated with one or more frames, or any combination thereof, orany other suitable representation of the particular pause points toserve as a refresher to the user of the location in media asset 126 atwhich he or she left off. In some embodiments, in response to receivinga pause command or other command to cease access of a media asset, themedia application may capture one or more frames associated with thepause point and/or prior to the pause point for use in generating thepreview frames. In some embodiments, the media application may identifyframes (e.g., based on metadata of the frame and/or image or audioprocessing techniques to identify objects of interest) to be included inthe preview based on whether the frames contain memorable aspects, e.g.,a famous actor, a critical or exciting scene in the media asset, etc.

In some embodiments, preview frames may be presented at the userinterfaces of FIG. 2 in response to determining that a confidence scoreof whether the identified user interface inputs match user interfaceinputs associated with the first user interaction profile or the seconduser interaction profile is below a predefined threshold. For example,if the media application determines that a likelihood of user interfaceinputs of the current consumption session matching a particular userinteraction profile is below a threshold of, e.g., a score of 50%,preview frames 208, 210 may be presented prior to generating forpresentation media asset 126 from the selected pause point, to receiveuser confirmation of the correct pause point based on the preview frameprior to generating for display media asset 126 from the selected pauseposition.

In some embodiments, to avoid showing a user one or more spoilers inconnection with the preview frames of a progress point of media asset126 that he or she has not yet reached, the media application mayprovide the preview frames 208, 210 one at a time, where the order ofproviding the preview frames corresponds to first showing an earlierpause point preview frame within the presentation of media asset 126.For example, user input may be received indicating that frame 208 doesnot correspond to the pause point of the user associated with thecurrent consumption session, and in response to receiving such input,preview frame 210 may be generated for presentation to enable userselection of preview frame 210 (or media asset 126 may be generated forpresentation from the pause point indicated at 204, if such pause pointis the only remaining stored pause point after receiving the userinput). In some embodiments, if the media application determines thatthe pause point indicated at 202 is more likely to correspond to theuser associated with the current consumption session than the pausepoint indicated at 204, preview frame 208 associated with the pausepoint indicated at 202 may be displayed in an emphasized manner ascompared to preview frame 210, e.g., larger, more conspicuous colorscheme or formatting, and/or more prominent position within userinterface 201. In some embodiments, using the techniques discussed inconnection with FIG. 1 , the media application may predict which pausepoint corresponds to a particular user, and may highlight a certainpreview frame corresponding to that pause point, or sort the previewframes to show the preview frame associated with the predicted pausepoint to be first within the list of preview frames, such as, forexample, at a top of the screen or otherwise more prominently shown tothe user.

User interface 203 may be provided by the media application inconnection with media asset 214, e.g., a movie titled “The Dark Knight,”where multiple pause points indicated at 216, 218 may be stored inconnection with media asset 214, where the pause points 216, 218 mayrespectively correspond to preview frames 220, 222. User interface 203may further include selectable option 224 to restart the presentation ofmedia asset 126 from a beginning of media asset 126. In someembodiments, the preview frames (e.g., preview frames 220, 222) forparticular pause points may correspond to I-Frames of one or moresegments that immediately precede the pause points. For example, if oneof the pause points corresponds to segment 500 in the manifest of mediaasset 214, then the I-frames from previous segments may be displayed insuccession (e.g., I-Frames from 495, 496, etc.). In some embodiments,one or more I-frames associated with a main plot or other significantscene occurring prior to the pause point indicated at 218, but after thepause point indicated at 216, may be used. In some embodiments, anaudiovisual clip may be used as preview 220 in response to determiningthat preview 220 is associated with the earliest stored pause point formedia asset 214, whereas preview 222 may correspond to still images,e.g., to avoid preview 222 acting as a spoiler to a user associated withthe pause point indicated at 216, whereas the same concerns may notexist for preview 220 associated with the pause point indicated at 216,since the user of the current consumption session is likely associatedwith pause point 216 or pause point 218 and thus either way hasencountered the frames associated with preview frame 220.

In some embodiments, the media application permits a user to performpause and resume operations using his or her mobile device, and thepause point may be saved on the mobile device and/or at remote storageaccessible by the mobile device. Thus, the pause point may be associatedwith a specific mobile device, regardless of whether a media account isassociated with multiple profiles. In such scenario, if the mediaapplication determines that a mobile device requesting access to a mediaasset associated with multiple pause points is the same mobile devicethat is indicated in a particular user interaction profile (e.g., theuser is attempting to resume the media asset using the mobile device asa remote control in a current consumption session, and the userpreviously used the mobile device to interact with the media asset oranother media asset in a prior consumption session), the pause pointassociated with the particular user interaction profile comprising theindication of the mobile device may be automatically selected. In someembodiments, such pause point may be automatically selected based on themedia application computing a high confidence score (e.g., exceeding apredefined threshold) that the current consumption session is associatedwith the particular user interaction profile comprising the indicationof the mobile device. In some embodiments, such high confidence scorecauses the presentation of the previews of FIG. 2 to be conditional,e.g., there may be no need to present a preview frame of any pausepoints, or present any other pause points, since the media applicationis sufficiently confident that the current consumption sessioncorresponds to the particular user interaction profile, on the basis ofthe same mobile device being associated with each of the currentconsumption session and particular user interaction profile associatedwith the prior consumption session that also utilized the mobile device.

User interface 205 may be provided by the media application inconnection with media asset collection 226, e.g., an episodic series ofa plurality of episodes spanning one or more seasons. User interface 205may comprise the pause points indicated at 228, 230, 232 for respectiveepisodes of media asset collection 226 from one or more seasons thereof,where the pause points indicated at 228, 230, 232 may respectivelycorrespond to preview frames 234, 236, 238. In some embodiments, if themedia application receives selection of, e.g., identifier 108, userinterface 205 may be generated for presentation comprising a list ofeach episode of the series associated with identifier 108 having astored pause point. In some embodiments, a short recap of the plot ofthe media asset prior to the selected pause point may be automaticallypresented or provided for user selection to view, depending on a lengthof time since last viewing the media asset, to refresh a user’s memory.

FIG. 3 shows a block diagram of an illustrative system 300 forassociating a current progress point of a media asset with one or moreuser profiles associated with a media application account, in accordancewith some embodiments of this disclosure. The media application maygenerate for display user interface 303 comprising one or more mediaasset identifiers 308, 310, 312, 314 corresponding to respective mediaassets, during a consumption session associated with the mediaapplication and user 302. In some embodiments, media asset identifiers308 and 310 may be associated with media asset category 316, and mediaasset identifiers 112 and 114 may be associated with media assetcategory 318. User interface 303 may comprise search bar 320 at whichqueries for media assets may be received from a user. Media asset 326may be generated for display from a broadcast or stream received at userequipment device 305 in association with the media application, or froma recording stored in a memory of user equipment device 305 and/or aremote server. User equipment device 305 may be, e.g., a televisionand/or may include an integrated display, e.g., on a smartphone ortablet, or may be connected to an external display device, e.g., atelevision.

In some embodiments, users 302 and 304 may be, e.g., members of the samehousehold taking part in a group consumption session in association withthe media application, accessing the media application using a userprofile 321 of user 302, where each of user 302 and 304 may beassociated with a respective user profile within a single account of themedia application. The media application may generate for consumptionmedia asset 326 based on input received from user 302 or user 304.During the playing of media asset 326, user 304 may need to stopconsuming media asset 326 for any of a variety of reasons, but user 302may desire to continue consuming media asset 326 (being viewed on theuser profile of user 302) at the current time. User 304 may desire topreserve information related to progress point or pause point 324, sinceuser 304 may wish to continue consuming media asset 326 at a later time,and user 304 may wish to avoid forgetting which media asset he or shewas consuming with user 302 during the group consumption session as wellas forgetting a progress point of the media asset when user 304 stoppedconsuming media asset 326. The media application may provide selectableoption 331 to associate pause point 324 with one or more user profilesassociated with the account of the media application. In someembodiments, selectable option 331 may be generated for display as anoverlay, overlapping media asset 326. In some embodiments, selectableoption 331 may be implemented as a special command, e.g., “Pause toResume on Profile B” which enables a user (e.g., user B corresponding touser 304) associated with profile B (corresponding to profile 323) toresume the media asset from the associated progress point from his orher own profile.

Selectable option 331 may be provided by the media application inresponse to one or more of a variety of occurrences. For example, uponreceiving a pause command associated with identifier 328 (or any othersuitable input during playing of media asset 326) such as, for example,from user 302 or user 304, the media application may generate forpresentation selectable option 331. In some embodiments, selectableoption 331 may comprise a list indicating each user profile associatedwith the account and an icon (e.g., a checkbox) for each respective userprofile, to enable selection of any suitable number of user profiles tobe associated with progress point 324. In some embodiments, selectableoption 331 may be provided based on receiving input indicating whichusers are consuming content during a current consumption session. Insome embodiments, if a current time of the current consumption sessioncorresponds to a time that user 304 typically consumes content, e.g., asindicated in the user profile of user 304 stored at database 325, themedia application may determine that user 304 is likely involved in theconsumption session, and thus may determine to provide selectable option331, e.g., when a pause command is received or when playing of mediaasset 326 is otherwise ceased prior to the end of media asset 326. Insome embodiments, selectable option 331 may be provided in response todetermining that media asset 326 is similar to media assets associatedwith the user profile of user 304, e.g., if user 304 recently watchedthe previous episode in the season of episodes associated with mediaasset 326. In some embodiments, selectable option 331 may be provided inresponse to determining that user 304 is leaving a vicinity of userequipment device 305. For example, sensor data determined by one or moresensors (e.g., a camera, biometric sensor, smart lock, etc.) may be usedto identify the presence of user 304 during the group consumptionsession and his or her subsequent exiting of the vicinity of userequipment device 305.

In some embodiments, a second screen device 309 (e.g., a smart phoneassociated with the user profile of user 304) may be in communicationover a network (e.g., network 606 of FIG. 6 ) with user equipment device305. The media application may determine, e.g., based on varyingReceived Signal Strength Indicator (RSSI) signals between second screendevice 309 and user equipment device 305, that user 304 was initiallypresent during the current consumption session but is now exiting thevicinity of user equipment device 305, and in response to thisdetermination may provide selectable option 331 at second screen device309 or at user equipment device 305. In some embodiments, selectableoption 331 may be provided by the media application on second screendevice 309, e.g., so as not to interrupt the consumption session of user302 when user 304 is not able to continue consuming media asset 326.Selectable option 331 may be provided to second screen device 309 in anysuitable manner, e.g., via an email message to an email addressspecified in the user profile, via a text message to a phone numberspecified in user profile, a notification in association with a mobileapplication associated with the media application, etc. Conversely, themedia application may decline to provide selectable option 331 upondetermining that user 302 is likely to be consuming content alone. Forexample, such determination may be made based on input from the user,sensor data indicating user 302 is alone, determining that media asset326 is unrelated to media assets indicated as being consumed inconnection with other user profiles stored in database 325, or anycombination thereof. While selectable option 331 is shown in the exampleof FIG. 3 as providing the capability of associating pause point 324with user profile 323 associated with user 304, one or more selectableoptions may be provided in accordance with the aforementioned techniquesto provide multiple user profiles (e.g., each user profile associatedwith the account) the option of associating pause point 324 with therespective user profile.

The media application may provide user interface 307 in connection witha subsequent second consumption session that is associated with userprofile 323 and user 304. The second consumption session may occur inassociation with user equipment device 305, or any other suitable devicecapable of running the media application and providing content to user304. The media application may determine that media asset 326 associatedwith identifier 308 of user interface 307 is associated with pause point324, based on an indication stored in connection with user profile 323stored in database 325, based on an affirmative selection (“Yes”) ofselectable option 331 in connection with the first consumption session,e.g., the group consumption session of user 302 and 304. In someembodiments, in response to receiving selection of identifier 308, themedia application may automatically resume playing of media asset 326from pause point 324 having been associated with user profile 323, asshown at user interface 311 of user equipment device 305. In someembodiments, selectable option 333 may be provided, prior to generatingfor presentation user interface 311, to enable user 304 to confirm thathe or she wishes to resume from pause point 324 of media asset 326. Insome embodiments, preview frames associated with pause point 324, suchas discussed in connection with FIG. 2 , may be employed in connectionwith the example of FIG. 3 , e.g., preview frames of pause point 324 maybe provided to user 304 to ensure that he or she wishes to resume frompause point 324.

In some embodiments, the techniques of FIG. 3 may be used within ahousehold even if users are accessing different accounts within themedia application that are unrelated to each other. For example, themedia application may detect that historically, multiple accounts havingdifferent login credentials have been accessed from a particular IPaddress (e.g., associated with a particular household). Using thetechniques of FIG. 3 , the media application may determine that a firstuser associated with the first account and a second user associated witha separate second account are consuming content together, and provide anoption to a second user to associate a progress point associated withthe first account with the second account.

FIG. 4 shows illustrative data structure 400 of user interactionprofiles stored in a user consumption data database, in accordance withsome embodiments of this disclosure. Data structure 400 may be stored indatabase 125 (which may correspond to database 325), and may compriseany suitable amount or types of data (e.g., user interface inputs,consumption data) associated with respective users of the mediaapplication. For example, column 402 may correspond to identifiers ofuser interaction profiles or user profiles associated with a particularaccount of the media application; column 404 may correspond toidentifiers of time stamps of consumed media assets; column 406 maycorrespond to progress points or pause points of consumed media assets;column 408 may correspond to the average amount of time a user browsesbefore viewing a media asset; column 410 may correspond to the mostcommon browsing method used to find media asset (e.g., scrolling throughmedia asset identifiers, or searching via a query for media assets);column 412 may correspond to the most visited section of the mediaapplication (e.g., “New Releases,” “Continue Watching,” etc.); column414 may correspond to an average scroll rate (e.g., how fast aparticular user scrolls through the media application) and/or a scrolldepth (e.g., a percentage of a particular screen a user typicallyscrolls through prior to consuming content); column 416 may correspondto a typical amount of trick play functions (e.g., fast-forward, rewind,skip, variable speed consumption) during consumption sessions; column418 may correspond to a typical duration of consumption sessions by theuser, such as based on a day of the week or time of day; column 420 maycorrespond to a frequency of skipping supplemental content (e.g.,advertisements); and column 422 may correspond to an IP address or otheridentifier of a mobile device of a particular user, e.g., used toconsume content or as a remote control to control playing of a mediaasset on user equipment device 305. In some embodiments, data structure400 may comprise metadata indicating attributes of consumed mediaassets, e.g., genre, actors, keywords, director, etc.).

The user account and/or user profile and/or user interaction profileinformation stored in association with data structure 400 may be builtover time by monitoring user interface inputs and user interactions withthe media application over time, and may be utilized in the examples ofFIGS. 1-3 , e.g., in selecting a pause point for resuming a media assetand associating a progress point or pause point of a first user profilewith a second user profile. In some embodiments, machine learningtechniques may be employed, such as training one or more machinelearning models based on data stored at data structure 400 (e.g.,labeled as corresponding to a particular user profile), to classifyreceived user interface inputs as likely to be associated with aparticular user profile.

In some embodiments, based on the data stored in column 422, the mediaapplication may determine when a command (e.g., a pause command orresume command) received from a particular user device or second screendevice matches a stored identifier of a particular user device or secondscreen device. In such instance, a pause point associated with the userinteraction profile corresponding to the particular user device orsecond screen device may be identified as the relevant profile for thecurrent consumption session, and presentation of the media asset may beautomatically resumed from the pause point, or resumed after receivingconfirmation of the user (e.g., with or without providing any previewframes prior to the resumption). In some embodiments, the mediaapplication may store the pause point locally on the user device orsecond screen device (or on a remote server), to enable a user to resumethe media asset from the pause point on his or her user device.

In some embodiments, a confidence score may be generated while a user isnavigating to a content item, based on comparing user interface inputsof a current consumption session with one or more attributes stored indata structure 400. For example, the media application may computeconfidence scores for respective user interaction profiles with respectto user interface inputs of a current consumption session, e.g., basedon a similarity between the stored data attributes and the monitoredinteractions during the current consumption session. In someembodiments, one or more of the columns of data structure 400 may beweighted based on predictive value to identifying a particular user. Forexample, if the media application determines an identifier associatedwith a mobile device being used in a consumption session matches anidentifier of a mobile device specified in column 422, suchdetermination may, in some circumstances, be enough on its own to causea confidence score to be computed that is sufficiently high to select apause point or progress point associated with the user interactionprofile having the matching mobile device identifier.

In some embodiments, the determination of whether to present a previewor not may be dependent on the value of the confidence score describedearlier (e.g., a preview may not be presented if the mobile devicedetected in a current consumption session matches a particular userinteraction profile stored in data structure 400). In some embodiments,in response to a computed confidence score exceeding a predeterminedthreshold, the media application may start pre-fetching a portion of thecontent (e.g., from the pause point) in order to reduce the time tofirst byte (TTFB). Such pre-fetching enables the media application topreload (e.g., locally pre-buffer and/or pre-cache) portions of themedia asset from the predicted pause point, which can reduce latency indelivery of content to a user, thereby reducing amount of time that auser waits for content to load and enhancing the user experience.

In some embodiments, the media application may predict which pause pointto present from among multiple pause points based on historical dataassociated with various commands (e.g., resume functions) performed inthe past. For example, a user might be in the habit of watching aspecific series at particular times on particular days. All commands maybe collected and associated with a time stamp in order to establish apattern and predict which pause point to present based on the time acommand is received, and additionally, a user’s navigation patterns maybe tracked and used to identify a user as compared to navigationpatterns of other users. For example, one user in a household mightscroll quickly to get to section of a screen (e.g., Continue Watchingsection), while another user might get to the desired content bysearching it for it (e.g., by entering the first few letters of thetitle), e.g., since it might be quicker to get to the content this way.Accordingly, such historical navigation patterns can be used to predictwhich pause point to present based on users with specific navigationpatterns and previously chosen pause points. In some embodiments,navigation profiles may be developed over time based on data collectedabout how users interact with the system, e.g., scrolling rate, as wellas actions received while content is consumed or the manner of consumingcontent (e.g., perform trick play functions more often than other users,binge-watch, spend a certain time watching per consumption session,whether and how long breaks are taken between episodes, whether and howoften a command to skip commercials is selected when available, etc.).

In some embodiments, the media application may delete a stored pausepoint from data structure 400 in response to receiving user input toresume playback of content from the particular pause point. In someembodiments, the new pause point for a particular user may be updated inresponse to receiving a pause command or in response to detereminingthat consumption of a media asset is stopped.

FIGS. 5-6 describe illustrative devices, systems, servers, and relatedhardware for generating for presentation a media asset starting from aselected pause point and associating a current progress point of a mediaasset with one or more user profiles associated with a media applicationaccount, in accordance with some embodiments of the present disclosure.FIG. 5 shows generalized embodiments of illustrative user equipmentdevices 500 and 501, which may correspond to, e.g., user equipmentdevice 105 of FIG. 1 , user equipment devices 305, 309 of FIG. 3 . Forexample, user equipment device 500 may be a smartphone device. Inanother example, user equipment device 501 may be a user televisionequipment system or device. User television equipment device 501 mayinclude set-top box 516. Set-top box 516 may be communicativelyconnected to microphone 518, speaker 514, and display 512. In someembodiments, microphone 518 may receive voice commands for the mediaapplication. In some embodiments, display 512 may be a televisiondisplay or a computer display. In some embodiments, set-top box 516 maybe communicatively connected to user input interface 510. In someembodiments, user input interface 510 may be a remote control device.Set-top box 516 may include one or more circuit boards. In someembodiments, the circuit boards may include control circuitry,processing circuitry, and storage (e.g., RAM, ROM, hard disk, removabledisk, etc.). In some embodiments, the circuit boards may include aninput/output path. More specific implementations of user equipmentdevices are discussed below in connection with FIG. 6 . Each one of userequipment device 500 and user equipment device 501 may receive contentand data via input/output (I/O) path 502. I/O path 502 may providecontent (e.g., broadcast programming, on-demand programming, Internetcontent, content available over a local area network (LAN) or wide areanetwork (WAN), and/or other content) and data to control circuitry 504,which includes processing circuitry 506 and storage 508. Controlcircuitry 504 may be used to send and receive commands, requests, andother suitable data using I/O path 502, which may comprise I/Ocircuitry. I/O path 502 may connect control circuitry 504 (andspecifically processing circuitry 506) to one or more communicationspaths (described below). I/O functions may be provided by one or more ofthese communications paths, but are shown as a single path in FIG. 5 toavoid overcomplicating the drawing.

Control circuitry 504 may be based on any suitable control circuitrysuch as processing circuitry 506. As referred to herein, controlcircuitry should be understood to mean circuitry based on one or moremicroprocessors, microcontrollers, digital signal processors,programmable logic devices, field-programmable gate arrays (FPGAs),application-specific integrated circuits (ASICs), etc., and may includea multi-core processor (e.g., dual-core, quad-core, hexa-core, or anysuitable number of cores) or supercomputer. In some embodiments, controlcircuitry may be distributed across multiple separate processors orprocessing units, for example, multiple of the same type of processingunits (e.g., two Intel Core i7 processors) or multiple differentprocessors (e.g., an Intel Core i5 processor and an Intel Core i7processor). In some embodiments, control circuitry 504 executesinstructions for the media application stored in memory (e.g., storage508). Specifically, control circuitry 504 may be instructed by the mediaapplication to perform the functions discussed above and below. In someimplementations, processing or actions performed by control circuitry504 may be based on instructions received from the media application.

In client/server-based embodiments, control circuitry 504 may includecommunications circuitry suitable for communicating with a mediaapplication server or other networks or servers. The instructions forcarrying out the above mentioned functionality may be stored on a server(which is described in more detail in connection with FIG. 6 ).Communications circuitry may include a cable modem, an integratedservices digital network (ISDN) modem, a digital subscriber line (DSL)modem, a telephone modem, Ethernet card, or a wireless modem forcommunications with other equipment, or any other suitablecommunications circuitry. Such communications may involve the Internetor any other suitable communication networks or paths (which isdescribed in more detail in connection with FIG. 6 ). In addition,communications circuitry may include circuitry that enables peer-to-peercommunication of user equipment devices, or communication of userequipment devices in locations remote from each other (described in moredetail below).

Memory may be an electronic storage device provided as storage 508 thatis part of control circuitry 504. As referred to herein, the phrase“electronic storage device” or “storage device” should be understood tomean any device for storing electronic data, computer software, orfirmware, such as random-access memory, read-only memory, hard drives,optical drives, digital video disc (DVD) recorders, compact disc (CD)recorders, BLU-RAY disc (BD) recorders, BLU-RAY 3D disc recorders,digital video recorders (DVR, sometimes called a personal videorecorder, or PVR), solid state devices, quantum storage devices, gamingconsoles, gaming media, or any other suitable fixed or removable storagedevices, and/or any combination of the same. Storage 508 may be used tostore various types of content described herein as well as mediaapplication data described above. Nonvolatile memory may also be used(e.g., to launch a boot-up routine and other instructions). Cloud-basedstorage, described in relation to FIG. 5 , may be used to supplementstorage 508 or instead of storage 508.

Control circuitry 504 may include video generating circuitry and tuningcircuitry, such as one or more analog tuners, one or more MPEG-2decoders or other digital decoding circuitry, high-definition tuners, orany other suitable tuning or video circuits or combinations of suchcircuits. Encoding circuitry (e.g., for converting over-the-air, analog,or digital signals to MPEG signals for storage) may also be provided.Control circuitry 504 may also include scaler circuitry for upconvertingand downconverting content into the preferred output format of userequipment 500. Control circuitry 504 may also include digital-to-analogconverter circuitry and analog-to-digital converter circuitry forconverting between digital and analog signals. The tuning and encodingcircuitry may be used by user equipment device 500, 501 to receive andto display, to play, or to record content. The tuning and encodingcircuitry may also be used to receive guidance data. The circuitrydescribed herein, including for example, the tuning, video generating,encoding, decoding, encrypting, decrypting, scaler, and analog/digitalcircuitry, may be implemented using software running on one or moregeneral purpose or specialized processors. Multiple tuners may beprovided to handle simultaneous tuning functions (e.g., watch and recordfunctions, picture-in-picture (PIP) functions, multiple-tuner recording,etc.). If storage 508 is provided as a separate device from userequipment device 500, the tuning and encoding circuitry (includingmultiple tuners) may be associated with storage 508.

Control circuitry 504 may receive instruction from a user by way of userinput interface 510. User input interface 510 may be any suitable userinterface, such as a remote control, mouse, trackball, keypad, keyboard,touch screen, touchpad, stylus input, joystick, voice recognitioninterface, or other user input interfaces. Display 512 may be providedas a stand-alone device or integrated with other elements of each one ofuser equipment device 500 and user equipment device 501. For example,display 512 may be a touchscreen or touch-sensitive display. In suchcircumstances, user input interface 510 may be integrated with orcombined with display 512. Display 512 may be one or more of a monitor,a television, a display for a mobile device, or any other type ofdisplay. A video card or graphics card may generate the output todisplay 512. The video card may be any control circuitry described abovein relation to control circuitry 504. The video card may be integratedwith control circuitry 504. Speakers 514 may be provided as integratedwith other elements of each one of user equipment device 500 and userequipment system 501 or may be stand-alone units. The audio component ofvideos and other content displayed on display 512 may be played throughthe speakers 514. In some embodiments, the audio may be distributed to areceiver (not shown), which processes and outputs the audio via speakers514.

The media application may be implemented using any suitablearchitecture. For example, it may be a stand-alone applicationwholly-implemented on each one of user equipment device 500 and userequipment device 501. In such an approach, instructions of theapplication are stored locally (e.g., in storage 508), and data for useby the application is downloaded on a periodic basis (e.g., from anout-of-band feed, from an Internet resource, or using another suitableapproach). Control circuitry 504 may retrieve instructions of theapplication from storage 508 and process the instructions to providesupplemental content as discussed. Based on the processed instructions,control circuitry 504 may determine what action to perform when input isreceived from user input interface 510. For example, movement of acursor on a display up/down may be indicated by the processedinstructions when user input interface 510 indicates that an up/downbutton was selected.

In some embodiments, the media application is a client/server-basedapplication. Data for use by a thick or thin client implemented on eachone of user equipment device 500 and user equipment device 501 isretrieved on-demand by issuing requests to a server remote to each oneof user equipment device 500 and user equipment device 501. In oneexample of a client/server-based guidance application, control circuitry504 runs a web browser that interprets web pages provided by a remoteserver. For example, the remote server may store the instructions forthe application in a storage device. The remote server may process thestored instructions using circuitry (e.g., control circuitry 511) toperform the operations discussed in connection with FIGS. 1-4 .

In some embodiments, the media application may be downloaded andinterpreted or otherwise run by an interpreter or virtual machine (runby control circuitry 504). In some embodiments, the media applicationmay be encoded in the ETV Binary Interchange Format (EBIF), received bycontrol circuitry 504 as part of a suitable feed, and interpreted by auser agent running on control circuitry 504. For example, the mediaapplication may be an EBIF application. In some embodiments, the mediaapplication may be defined by a series of JAVA-based files that arereceived and run by a local virtual machine or other suitable middlewareexecuted by control circuitry 504. In some of such embodiments (e.g.,those employing MPEG-2 or other digital media encoding schemes), themedia application may be, for example, encoded and transmitted in anMPEG-2 object carousel with the MPEG audio and video packets of aprogram.

FIG. 6 is a diagram of an illustrative system 600 for associating acurrent progress point of a media asset with one or more user profilesassociated with a media application account, in accordance with someembodiments of this disclosure. User equipment devices 607, 608, 610(e.g., which may correspond to one or more of user equipment device 105of FIG. 1 , user equipment devices 305, 309 of FIG. 3 ) may be coupledto communication network 606. Communication network 606 may be one ormore networks including the Internet, a mobile phone network, mobilevoice or data network (e.g., a 5G, 4G, or LTE network), cable network,public switched telephone network, or other types of communicationnetwork or combinations of communication networks. Paths (e.g., depictedas arrows connecting the respective devices to the communication network606) may separately or together include one or more communicationspaths, such as a satellite path, a fiber-optic path, a cable path, apath that supports Internet communications (e.g., IPTV), free-spaceconnections (e.g., for broadcast or other wireless signals), or anyother suitable wired or wireless communications path or combination ofsuch paths. Communications with the client devices may be provided byone or more of these communications paths but are shown as a single pathin FIG. 6 to avoid overcomplicating the drawing.

Although communications paths are not drawn between user equipmentdevices, these devices may communicate directly with each other viacommunications paths as well as other short-range, point-to-pointcommunications paths, such as USB cables, IEEE 1394 cables, wirelesspaths (e.g., Bluetooth, infrared, IEEE 702-11x, etc.), or othershort-range communication via wired or wireless paths. The userequipment devices may also communicate with each other directly throughan indirect path via communication network 606.

System 600 may comprise media content source 602 and server 604. In someembodiments, media content source 602 may correspond to server 604and/or media content source 602 and server 604 may be under the controlof or otherwise associated with a media content provider. In addition,there may be more than one of each of media content source 602 andserver 604, but only one of each is shown in FIG. 6 to avoidovercomplicating the drawing. If desired, media content source 602 andserver 604 may be integrated as one source device. In some embodiments,the media application may be executed at one or more of controlcircuitry 611 of server 604 (and/or control circuitry of user equipmentdevices 607, 608, 610). In some embodiments, database 125 of FIG. 1 ,which may correspond to database 325 of FIG. 3 , and associated withdata structure 400 of FIG. 4 , may be stored at database 605 maintainedat or otherwise associated with server 604.

In some embodiments, server 604 may include control circuitry 611 andstorage 614 (e.g., RAM, ROM, Hard Disk, Removable Disk, etc.). Storage614 may store one or more databases. Server 604 may also include aninput/output path 612. I/O path 612 may provide device information, orother data, over a local area network (LAN) or wide area network (WAN),and/or other content and data to control circuitry 611, which mayinclude processing circuitry, and storage 614. Control circuitry 611 maybe used to send and receive commands, requests, and other suitable datausing I/O path 612, which may comprise I/O circuitry. I/O path 612 mayconnect control circuitry 611 (and specifically control circuitry) toone or more communications paths.

Control circuitry 611 may be based on any suitable control circuitrysuch as one or more microprocessors, microcontrollers, digital signalprocessors, programmable logic devices, field-programmable gate arrays(FPGAs), application-specific integrated circuits (ASICs), etc., and mayinclude a multi-core processor (e.g., dual-core, quad-core, hexa-core,or any suitable number of cores) or supercomputer. In some embodiments,control circuitry 611 may be distributed across multiple separateprocessors or processing units, for example, multiple of the same typeof processing units (e.g., two Intel Core i7 processors) or multipledifferent processors (e.g., an Intel Core i5 processor and an Intel Corei7 processor). In some embodiments, control circuitry 611 executesinstructions for an emulation system application stored in memory (e.g.,the storage 614). Memory may be an electronic storage device provided asstorage 614 that is part of control circuitry 611.

In some embodiments, server 604 may retrieve guidance data from mediacontent source 602, process the data as will be described in detailbelow, and forward the data to user equipment devices 607, 608, 610.Media content source 602 may include one or more types of contentdistribution equipment including a television distribution facility,cable system headend, satellite distribution facility, programmingsources (e.g., television broadcasters, such as NBC, ABC, HBO, etc.),intermediate distribution facilities and/or servers, Internet providers,on-demand media servers, and other content providers. NBC is a trademarkowned by the National Broadcasting Company, Inc., ABC is a trademarkowned by the American Broadcasting Company, Inc., and HBO is a trademarkowned by the Home Box Office, Inc. Media content source 602 may be theoriginator of content (e.g., a television broadcaster, a Webcastprovider, etc.) or may not be the originator of content (e.g., anon-demand content provider, an Internet provider of content of broadcastprograms for downloading, etc.). Media content source 602 may includecable sources, satellite providers, on-demand providers, Internetproviders, over-the-top content providers, or other providers ofcontent. Media content source 602 may also include a remote media serverused to store different types of content (including video contentselected by a user), in a location remote from any of the clientdevices. Media content source 602 may also provide supplemental contentrelevant to the metadata of a particular scene of a media asset asdescribed above.

Client devices may operate in a cloud computing environment to accesscloud services. In a cloud computing environment, various types ofcomputing services for content sharing, storage or distribution (e.g.,video sharing sites or social networking sites) are provided by acollection of network-accessible computing and storage resources,referred to as “the cloud.” For example, the cloud can include acollection of server computing devices (such as, e.g., server 604),which may be located centrally or at distributed locations that providecloud-based services to various types of users and devices connected viaa network such as the Internet via communication network 606. In suchembodiments, user equipment devices may operate in a peer-to-peer mannerwithout communicating with a central server.

FIG. 7 is a flowchart of a detailed illustrative process 700 forgenerating for presentation a media asset starting from a selected pausepoint, in accordance with some embodiments of this disclosure. Invarious embodiments, the individual steps of process 700 may beimplemented by one or more components of the devices and systems ofFIGS. 1-6 . Although the present disclosure may describe certain stepsof process 700 (and of other processes described herein) as beingimplemented by certain components of the devices and systems of FIGS.1-6 , this is for purposes of illustration only, and it should beunderstood that other components of the devices and systems of FIGS. 1-6may implement those steps instead.

At 702, control circuitry (e.g., control circuitry 611 of server 604 ofFIG. 6 and/or control circuitry of user equipment device 105 of FIG. 1 )may monitor user interface inputs received by a media application (e.g.,running at user equipment device 105 and/or server 604) over time. Forexample, the control circuitry may determine historical navigationpatterns and user interface inputs received during consumption of mediaassets (e.g., as shown at data structure 400 of FIG. 4 ).

At 704, the control circuitry may determine, based on the monitored userinterface inputs, a plurality of user interaction profiles forrespective users. For example, the determined historical navigationpatterns and user interface inputs may be correlated to respective userinteraction profiles (e.g., shown in column 402 of data structure 400 ofFIG. 4 ). In some embodiments, the media application associated with theuser interaction profiles may be a shared account or profile in whichusers do not have individualized accounts (e.g., discerning betweenusers of the account may not be possible via login credentials or byselecting a particular profile).

At 706, the control circuitry may receive a request (e.g., via userinterface 103 of FIG. 1 ) to view a media asset during a consumptionsession associated with a first user interaction profile (e.g., aprofile tracking historical user interface inputs and consumption dataof user 102, which may be transparent to user 102).

At 708, the control circuitry may generate for display the media asset(e.g., media asset 126 of FIG. 1 , on user equipment device 105 of FIG.1 ) based on a request from a first user (e.g., user 102 associated witha first user interaction profile). For example, the control circuitrymay generate for display the media asset in response to receivingselection of identifier 108.

At 710, the control circuitry may receive a pause command (e.g.,associated with icon 128 of FIG. 1 provided via user interface 109 ofFIG. 1 , such as via a remote control device coupled to user equipmentdevice 105) to freeze the playing of the media asset (e.g., media asset126 of FIG. 1 ) at pause point 124.

At 712, in response to receiving the pause command, the controlcircuitry may cause an indication of pause point 124 to be stored (e.g.,in association with the first interaction user profile at database 125of FIG. 1 ) in association with a time stamp of the media asset when thepause command is received. In some embodiments, metadata associated withthe partially consumed media asset and/or user interface inputsassociated with the current consumption session may be stored inconnection with the pause point.

At 714, the control circuitry may receive another request to view themedia asset (e.g., media asset 126 of FIG. 1 , on user equipment device105 of FIG. 1 or any other suitable device) during a consumption sessionassociated with a second user interaction profile. The request may bereceived from a second user (e.g., user 104 of FIG. 1 ), and theconsumption session may be associated with the same user account orprofile as the first consumption session associated with the first user,but occurring subsequent in time to such first consumption session.

At 716, the control circuitry may generate for display the media asset(e.g., the same media asset associated with the stored pause point ofthe first consumption session, media asset 126 of FIG. 1 , for displayon user equipment device 105 of FIG. 1 or any other suitable device)based on a request from the second user.

At 718, the control circuitry may receive a pause command (e.g.,associated with icon 128 provided by user interface 111 of FIG. 1 , suchas via a remote control device coupled to user equipment device 105) tofreeze the playing of the media asset (e.g., media asset 126 of FIG. 1 )at pause point 130. Pause point 130 may correspond to a differentlocation within media asset 126 than stored pause point 124.

At 720, in response to receiving the pause command at 718, the controlcircuitry may cause an indication of pause point 130 to be stored (e.g.,in association with the second interaction user profile at database 125of FIG. 1 ) in association with a time stamp of the media asset when thepause command is received. In some embodiments, metadata associated withthe partially consumed media asset and/or user interface inputsassociated with the current consumption session may be stored inconnection with the pause point.

At 722, the control circuitry may receive a request to access the mediaasset (e.g., media asset 126 of FIG. 1 , on user equipment device 105 ofFIG. 1 or any other suitable device) during a current consumptionsession, occurring after the first and second consumption sessionsrespectively associated with pause point 124 and 130. Such request maybe received from, e.g., user 102 or user 104 of FIG. 1 , although thecontrol circuitry may not be able to determine which user is associatedwith the current consumption session based on login credentials alone,since users 102 and 104 may each access a single shared account orprofile.

At 724, the control circuitry may identify user interface inputsreceived during the current consumption session. For example, thecontrol circuitry may determine that the request received at 722 isassociated with selecting identifier 108 from media category 116, or thecontrol circuitry may determine that the request received at 722 isassociated with selecting identifier 108 based on a search queryreceived at portion 120 of user interface 107. In some embodiments, thecontrol circuitry may take into account any number of suitable inputs orinteractions, e.g., the various attributes shown in data structure 400of FIG. 4 .

At 726, the control circuitry may compare the identified user interfaceinputs received during the current consumption session to user interfaceinputs associated with the first user interaction profile and seconduser interaction profile, e.g., stored in association with datastructure 400 of FIG. 4 . In some embodiments, the control circuitry maygenerate respective confidence scores based on a degree of similaritybetween the identified user interface inputs and the stored userinterface inputs for each of the first user interaction profile (e.g.,associated with user 102) and the second user interaction profile (e.g.,associated with user 104).

At 728, the control circuitry may determine whether the identified userinterface inputs match the first or second user interaction profile. Insome embodiments, the control circuitry may perform the determination byselecting the user interaction profile having the higher confidencescore as an indicator of a match. In some embodiments, the controlcircuitry may determine there is a match only if a particular userinteraction profile is associated with a confidence score that exceeds acertain predefined threshold (e.g., 50%), and may select the userinteraction profile having the higher confidence score if eachconfidence score exceeds the threshold.

At 730, the control circuitry may, in response to determining thatneither of the first user interaction profile or the second userinteraction profile constitutes a match, generate for display the mediaasset (e.g., media asset 126 of FIG. 1 , on user equipment device 105 ofFIG. 1 or any other suitable device) from the beginning. The controlcircuitry may perform this action based on the inference that the userof the current consumption session may be a new user, since the detecteduser interface inputs do not correspond to historical data of the userinteraction profiles. In some embodiments, the control circuitry mayprovide a prompt asking the user whether he or she previously viewed themedia asset, and in response to receiving an affirmative selection,present preview of stored pause points to the user, such as described inthe example illustrated in FIG. 3 .

At 732, the control circuitry may select the first or second pause pointbased on identified user interface inputs matching the first userinteraction profile or the second profile. For example, the controlcircuitry may select the first pause point (e.g., pause point 124 ofFIG. 1 ) in response to determining that the comparison at 726 resultsin a match between the first user interaction profile and the userinterface inputs of the current consumption session.

At 734, the control circuitry may generate for display the media asset(e.g., media asset 126 of FIG. 1 , on user equipment device 105 of FIG.1 or any other suitable device) from the selected pause point (e.g.,pause point 124). In some embodiments, such generating for display maybe performed automatically. In some embodiments, the user may beprompted to confirm to begin playing of the media asset at the selectedpause point.

FIG. 8 is a flowchart of a detailed illustrative process for generatingfor presentation a media asset starting from a selected pause point, inaccordance with some embodiments of this disclosure. In variousembodiments, the individual steps of process 800 may be implemented byone or more components of the devices and systems of FIGS. 1-6 .Although the present disclosure may describe certain steps of process800 (and of other processes described herein) as being implemented bycertain components of the devices and systems of FIGS. 1-6 , this is forpurposes of illustration only, and it should be understood that othercomponents of the devices and systems of FIGS. 1-6 may implement thosesteps instead.

At 802, control circuitry (e.g., control circuitry 611 of server 604 ofFIG. 6 and/or control circuitry of user equipment device 105 of FIG. 1 )may perform 726 of FIG. 7 , to compare identified user interface inputsreceived during the current consumption session to user interface inputsassociated with the first user interaction profile and the second userinteraction profile.

At 804, the control circuitry may determine confidence scores indicativeof whether a match exists with the first user interaction profile or thesecond user interaction profile. For example, the control circuitry maymonitor user inputs with user interface 103 to determine values for oneor more of the attributes shown in columns 402-422 of FIG. 4 , andcompare each value to respective values for such attributes associatedwith the first user interaction profile and the second user interactionprofile.

At 806, the control circuitry may determine whether the computedconfidence scores associated with the first interaction profile and thesecond interaction profile exceed a first threshold (e.g., 75%). Inresponse to determining one or more of the computed confidence scoresexceed the first threshold, processing may proceed to 808. On the otherhand, in response to determining one or more of the computed confidencescores do not exceed the first threshold, processing may proceed to 812.

At 808, the control circuitry may select a pause point (e.g., pausepoint 124 of FIG. 1 ) associated with a user interaction profile that isassociated with the confidence score exceeding the first threshold. Ifeach of the computed confidence scores associated with the firstinteraction profile and the second interaction profile exceeds the firstthreshold, the control circuitry may choose the higher of the twoscores.

At 810, the control circuitry may pre-fetch a portion of the media asset(e.g., media asset 126 of FIG. 1 , on user equipment device 105 of FIG.1 or any other suitable device) from the selected pause point (e.g.,pause point 124 of FIG. 1 ). For example, the control circuitry maypre-fetch any suitable number of segments from a manifest of the mediaasset, to buffer such segments in anticipation of the user resuming themedia asset from the selected pause point. At 816, the control circuitrymay decline to present preview frames associated with the selected pausepoint, based on the fact that the relatively high confidence score(e.g., exceeding the first threshold) associated with the selected pausepoint indicates a high level of certainty that the selected pause pointis correctly matched to the user interaction profile associated with thecurrent consumption session.

At 812, the control circuitry may, in response to determining thatneither of the computed confidence scores exceeds the first threshold,determine whether one or more of the confidence scores exceed the secondthreshold (e.g., 50%). If the control circuitry determines that neitherof the computed confidence scores exceeds the first threshold,processing may proceed to 726 of FIG. 7 . On the other hand, if thecontrol circuitry determines that at least one of the computedconfidence scores exceeds the first threshold, processing may proceed to818.

At 818, the control circuitry may select a pause point (e.g., pausepoint 124 of FIG. 1 ) associated with a user interaction profile that isassociated with the confidence score exceeding the second threshold(e.g., 50%). If each of the computed confidence scores associated withthe first interaction profile and the second interaction profile exceedsthe second threshold, the control circuitry may choose the higher of thetwo scores.

At 820, the control circuitry may present preview frames associated withthe selected pause point (e.g., pause point 124 of FIG. 1 ). Forexample, the control circuitry may generate for display user interface201 of FIG. 2 depicting multiple pause points and corresponding previewframes for media asset 126. At 820, user interface 205 may be generatedfor presentation by the control circuitry to depict each pause point,and respective previews, of each media asset in media asset collection226 (e.g., the episodic series “Outer Banks”).

At 822, the control circuitry may receive user selection to being themedia asset (e.g., media asset 126 of FIG. 1 , on user equipment device105 of FIG. 1 or any other suitable device) from the selected pausepoint. In some embodiments, such confirmation from the user may be bepresented only if the confidence score is below the second threshold, orsuch confirmation from the user may not be received at all, e.g., themedia asset may be automatically generated for display from the selectedpause point. 824 may be performed in a similar manner to 734 of FIG. 7 .

FIG. 9 is a flowchart of a detailed illustrative process 900 forassociating a current progress point of a media asset with one or moreuser profiles associated with a media application account, in accordancewith some embodiments of this disclosure. In various embodiments, theindividual steps of process 900 may be implemented by one or morecomponents of the devices and systems of FIGS. 1-6 . Although thepresent disclosure may describe certain steps of process 900 (and ofother processes described herein) as being implemented by certaincomponents of the devices and systems of FIGS. 1-6 , this is forpurposes of illustration only, and it should be understood that othercomponents of the devices and systems of FIGS. 1-6 may implement thosesteps instead.

At 902, control circuitry (e.g., control circuitry 611 of server 604 ofFIG. 6 and/or control circuitry of user equipment device 105 of FIG. 1 )may determine that a plurality of user profiles (e.g., profiles 321, 323of FIG. 3 ) are associated with an account of a media application, e.g.,a shared account having common login credentials, where multiple usersmay be permitted to maintain personalized profiles that track eachuser’s user interface inputs, navigation history and historicalconsumption habits.

At 904, the control circuitry may receive a request (e.g., from user 302of FIG. 3 , via user interface 303 provided by the media application) toview a media asset (e.g., media asset 326 of FIG. 3 ) during a firstconsumption session (e.g., associated with the first user 302)associated with the media account. The first consumption session maycorrespond to a group watching session, such as, for example, whereusers 302 and 304, each associated with a respective user profile, areconsuming one or more media assets in a group consumption session.

At 906, the control circuitry may generate for presentation the mediaasset (e.g., media asset 326 of FIG. 3 ) during the first consumptionsession associated with the account.

At 908, the control circuitry may generate for presentation a selectableoption (e.g., selectable option 331 of FIG. 3 ) to associate a currentprogress point (e.g., progress point 324 of FIG. 3 ) of the media assetwith one or more of the plurality of user profiles (e.g., user profile323) associated with the account.

At 910, control circuitry may receive a selection (e.g., an affirmativeselection of “Yes” in connection with user profile 323 of FIG. 3 ) ofone or more of the user profiles via the selectable option (e.g.,selectable option 331 of FIG. 3 ). In some embodiments, the selectableoption may be presented in a manner that enables a user to selectmultiple user profiles at once with which to associate the progresspoint (e.g., progress point 324 of FIG. 3 ). For example, the selectableoption may comprise an overlay or pop-up showing each user profile ofthe media account and corresponding user interface portions that enablea user to select the desired number of user profiles. In someembodiments, the control circuitry may cause the selectable option to bedisplayed on a second screen device (e.g., user device 309 of FIG. 3 ),and selection may be received at such device and transmitted to userequipment device 305 and/or server 604 for processing.

At 912, the control circuitry may, during a second consumption session,receive a request for accessing the media asset (e.g., media asset 326of FIG. 3 ). For example, the second consumption session may beassociated with user 304, and may occur at a later time than the firstconsumption session. The request for accessing the media asset may bereceived by detecting, via user interface 307, user selection ofidentifier 308.

At 914, the control circuitry may determine that the second consumptionsession is associated with the selected one or more user profiles. Forexample, the control circuitry may compare the selected one or more userprofiles (e.g., user profile 323, associated with an indication ofprogress point 324 of FIG. 3 , in data structure 400 of FIG. 4 , by wayof selectable option 331 of FIG. 3 ) to the user profile selected duringthe second user consumption session to determine whether there is amatch. If, however, at 914, the control circuitry determines that thesecond consumption decision is not associated with a particular profile,processing may proceed to 920.

At 916, in response to determining that the selected one or more userprofiles matches the user profile of the second consumption session, thecontrol circuitry may retrieve an indication of the progress point(e.g., from column 406 of FIG. 4 ) and request the media asset (e.g.,from server 604 of FIG. 6 ) from the progress point.

At 918, the control circuitry may resume the media asset (e.g., mediaasset 326 of FIG. 3 ) from the progress point associated with theselectable option (e.g., progress point 324 of FIG. 3 ). In someembodiments, such resumption may be performed automatically, or inresponse to receiving a confirmatory input from the user.

At 920, the control circuitry may generate for display the media asset(e.g., media asset 326 of FIG. 3 ) from the beginning, e.g., since noprogress points are determined to be associated with the particularmedia asset for the current user profile, the user may be determined tohave not yet consumed the media asset during any other consumptionsession.

FIG. 10 is a flowchart of a detailed illustrative process 1000 fordetermining whether to present a selectable option to associate acurrent progress point of a media asset with one or more user profilesassociated with a media application account, in accordance with someembodiments of this disclosure. In various embodiments, the individualsteps of process 1000 may be implemented by one or more components ofthe devices and systems of FIGS. 1-6 . Although the present disclosuremay describe certain steps of process 1000 (and of other processesdescribed herein) as being implemented by certain components of thedevices and systems of FIGS. 1-6 , this is for purposes of illustrationonly, and it should be understood that other components of the devicesand systems of FIGS. 1-6 may implement those steps instead.

At 1002, control circuitry (e.g., control circuitry 611 of server 604 ofFIG. 6 and/or control circuitry of user equipment device 105 of FIG. 1 )may determine whether user input indicating at least one user needs tostop consuming the media asset is received. For example, user interface303 provided by the media application at user equipment device 305 mayprovide a prompt for user 302 to indicate one or more other usersparticipating in the current consumption session. In the absence of suchinput, processing may proceed to 1004. Otherwise, processing may proceedto 908 of FIG. 9 , to provide a selectable option to the user toassociate the progress point (e.g., progress point 324 of FIG. 3 ) withone or more profiles.

At 1004, the control circuitry may determine, based on sensor data,whether at least one user previously in the vicinity of user equipmentdevice is leaving the vicinity of the user equipment device. Forexample, the control circuitry may receive sensor data from a camera,and process such sensor data, e.g., to perform facial recognitiontechniques to identify users in the captured image, such as by comparingextracted facial features from the image to facial features of an imageof a user stored in association with a user profile of the account). Anysuitable biometric sensor or other sensor may be used to ascertain thepresence of a user (e.g., user 304) in the vicinity of the userequipment device (e.g., user equipment device 305), and the subsequentexiting of such user from the vicinity. In response to an affirmativedetermination at 1004, processing may proceed to 908 of FIG. 9 .Otherwise, processing may proceed to 1006.

At 1006, the control circuitry may determine, based on one or more userprofiles (e.g., stored at data structure 400 of FIG. 4 ), whethermultiple users are likely to be viewing the media asset. For example, ifthe control circuitry determines that user 304 recently viewed the priorepisode of media asset 326 (e.g., at a similar time to the currenttime), the control circuitry may determine that user 304 is likely to beconsuming media asset 326 with user 302 in a group session. In responseto an affirmative determination at 1004, processing may proceed to 908of FIG. 9 . Otherwise, processing may proceed to 1008.

At 1008, the control circuitry may decline to generate for presentationthe selectable option (e.g., selectable option 331 of FIG. 3 ). 1008 maybe performed based on a determination that there is a lack of anyindicators that user 302 is accompanied by any other users having userprofiles associated with the user account of the media application, andthus there may be no need to provide the selectable option to associatea progress point with another profile.

FIG. 11 is a flowchart of a detailed illustrative process for storing anew pause point with a preview, in accordance with some embodiments ofthis disclosure. In various embodiments, the individual steps of process1100 may be implemented by one or more components of the devices andsystems of FIGS. 1-6 . Although the present disclosure may describecertain steps of process 1100 (and of other processes described herein)as being implemented by certain components of the devices and systems ofFIGS. 1-6 , this is for purposes of illustration only, and it should beunderstood that other components of the devices and systems of FIGS. 1-6may implement those steps instead.

At 1102, control circuitry (e.g., control circuitry 611 of server 604 ofFIG. 6 and/or control circuitry of user equipment device 105 of FIG. 1 )may receive input requesting access to a media asset (e.g., media asset126 of FIG. 1 , such as by way of selecting identifier 108). At 1104,the control circuitry may determine whether the user profile or useraccount associated with the current consumption session stores anindication of one or more pause points for the requested media asset. Ifyes, processing may proceed to 1108; otherwise, processing may proceedto 1106. At 1106, the control circuitry may cause the media asset to begenerated for display from the beginning. At 1108, the control circuitrymay provide a prompt to the user requesting confirmation of a particularpause point from which the media asset should be resumed. Alternatively,the media asset may be automatically resumed from a predicted pausepoint, using the techniques discussed in connection with FIG. 1 .

At 1110, the control circuitry may play the media asset from theselected pause position (e.g., pause position 124 of media asset 126 ofFIG. 1 ). At 1112, the control circuitry may detect that during thecurrent consumption session, a pause command has been received, thedevice being used to consumed the media asset has been turned off (e.g.,user equipment 105 of FIG. 1 ) or the user exited out of the mediaapplication or otherwise ceased consumption of the media asset. At 1114,the control circuitry may remove the selected pause point (e.g., pausepoint 124) from storage and overwrite or replace such pause point with anew pause point corresponding to the point of the media asset at whichthe user ceased access of the media asset at 1112. At 1116, the controlcircuitry may store such new pause point (e.g., at storage 614 of server604 of FIG. 6 ) based on such detecting that playing of the media assetpaused or stopped at 1112, and generate a preview (e.g., a 4-10 secondclip) of one or more frames associated with the new pause point.

The processes discussed above are intended to be illustrative and notlimiting. One skilled in the art would appreciate that the steps of theprocesses discussed herein may be omitted, modified, combined and/orrearranged, and any additional steps may be performed without departingfrom the scope of the invention. More generally, the above disclosure ismeant to be illustrative and not limiting. Only the claims that followare meant to set bounds as to what the present invention includes.Furthermore, it should be noted that the features and limitationsdescribed in any one embodiment may be applied to any other embodimentherein, and flowcharts or examples relating to one embodiment may becombined with any other embodiment in a suitable manner, done indifferent orders, or done in parallel. In addition, the systems andmethods described herein may be performed in real time. It should alsobe noted that the systems and/or methods described above may be appliedto, or used in accordance with, other systems and/or methods.

1-50. (canceled)
 51. A computer-implemented method comprising:determining that a plurality of user profiles are associated with anaccount of a media application; generating for presentation a mediaasset during a first consumption session associated with the account;generating for presentation a selectable option to associate a currentprogress point of the media asset with one or more of the plurality ofuser profiles associated with the account; receiving a selection of oneor more of the plurality of user profiles via the selectable option;during a second consumption session, receiving a request for accessingthe media asset; and in response to determining that the secondconsumption session is associated with the selected one or more userprofiles, resuming the media asset from the progress point associatedwith the selectable option.
 52. The method of claim 51, furthercomprising: in response to receiving the request for accessing the mediaasset and determining that the second consumption session is associatedwith the selected one or more user profiles, providing a selectableoption to resume the media asset from the progress point associated withthe selectable option.
 53. The method of claim 51, wherein the mediaasset is generated for presentation on a first device, and theselectable option is generated for presentation on the first device. 54.The method of claim 51, wherein the media asset is generated forpresentation on a first device, and the selectable option is generatedfor presentation on a second device in the vicinity of the first device.55. The method of claim 51, further comprising: determining that aplurality of users associated with respective user profiles of theplurality of user profiles are consuming the media asset during thefirst consumption session.
 56. The method of claim 55, whereindetermining that the plurality of users associated with respective userprofiles of the plurality of user profiles are consuming the media assetduring the first consumption session comprises: determining that a firstuser profile initiated the first consumption session; and determiningthat a second user profile comprises an indication that media assetsrelated to the media asset of the first consumption session werepreviously consumed.
 57. The method of claim 55, wherein determiningthat the plurality of users associated with respective user profiles ofthe plurality of user profiles are consuming the media asset during thefirst consumption session comprises: determining, based on sensor data,that users associated with a first user profile and a second userprofile, respectively, are consuming the media asset during the firstconsumption session.
 58. The method of claim 55, wherein determiningthat the plurality of users associated with respective user profiles ofthe plurality of user profiles are consuming the media asset during thefirst consumption session comprises: receiving input indicating that theusers associated with the first user profile and the second userprofile, respectively, are consuming the media asset during the firstconsumption session.
 59. The method of claim 51, further comprising:determining that a user associated with a particular user profile is notconsuming the media asset during the first consumption session; and inresponse to determining that the user associated with the particularuser profile is not consuming the media asset during the firstconsumption session, declining to generate for presentation theselectable option.
 60. The method of claim 51, wherein determining thatthe user associated with the particular user profile is not consumingthe media asset during the first consumption session comprises:determining that media assets indicated in the particular user profileare not related to the media asset being consumed during the firstconsumption session.
 61. A computer-implemented system comprising:memory; control circuitry configured to: determine that a plurality ofuser profiles, stored in the memory, are associated with an account of amedia application; generate for presentation a media asset during afirst consumption session associated with the account; generate forpresentation a selectable option to associate a current progress pointof the media asset with one or more of the plurality of user profilesassociated with the account; receive a selection of one or more of theplurality of user profiles via the selectable option; during a secondconsumption session, receive a request for accessing the media asset;and in response to determining that the second consumption session isassociated with the selected one or more user profiles, resume the mediaasset from the progress point associated with the selectable option. 62.The system of claim 61, wherein the control circuitry is furtherconfigured to: in response to receiving the request for accessing themedia asset and determining that the second consumption session isassociated with the selected one or more user profiles, provide aselectable option to resume the media asset from the progress pointassociated with the selectable option.
 63. The system of claim 61,wherein the control circuitry is configured to generate for presentationthe media asset on a first device, and generate for presentation theselectable option ion the first device.
 64. The system of claim 61,wherein the control circuitry is configured to generate for presentationthe media asset on a first device, and generate for presentation theselectable option on a second device in the vicinity of the firstdevice.
 65. The system of claim 61, wherein the control circuitry isfurther configured to: determine that a plurality of users associatedwith respective user profiles of the plurality of user profiles areconsuming the media asset during the first consumption session.
 66. Thesystem of claim 65, wherein the control circuitry is further configuredto determine that the plurality of users associated with respective userprofiles of the plurality of user profiles are consuming the media assetduring the first consumption session by: determining that a first userprofile initiated the first consumption session; and determining that asecond user profile comprises an indication that media assets related tothe media asset of the first consumption session were previouslyconsumed.
 67. The system of claim 65, wherein the control circuitry isconfigured to determine that the plurality of users associated withrespective user profiles of the plurality of user profiles are consumingthe media asset during the first consumption session by: determining,based on sensor data, that users associated with a first user profileand a second user profile, respectively, are consuming the media assetduring the first consumption session.
 68. The system of claim 65,wherein the control circuitry is configured to determine that theplurality of users associated with respective user profiles of theplurality of user profiles are consuming the media asset during thefirst consumption session by: receiving input indicating that the usersassociated with the first user profile and the second user profile,respectively, are consuming the media asset during the first consumptionsession.
 69. The system of claim 61, wherein the control circuitry isfurther configured to: determine that a user associated with aparticular user profile is not consuming the media asset during thefirst consumption session; and in response to determining that the userassociated with the particular user profile is not consuming the mediaasset during the first consumption session, decline to generate forpresentation the selectable option.
 70. The system of claim 61, whereinthe control circuitry is further configured to determine that the userassociated with the particular user profile is not consuming the mediaasset during the first consumption session by: determining that mediaassets indicated in the particular user profile are not related to themedia asset being consumed during the first consumption session. 71-100.(canceled)